-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update ZAP to tip. #21244
Merged
woody-apple
merged 1 commit into
sve
from
cherry-pick-a7ad1d8cd55c30bdcd6966d2e192695336166852
Jul 27, 2022
Merged
Update ZAP to tip. #21244
woody-apple
merged 1 commit into
sve
from
cherry-pick-a7ad1d8cd55c30bdcd6966d2e192695336166852
Jul 27, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This update stops guessing at fabric-scoping based on the types of struct/event fields and instead explicitly says which structs are fabric-scoped and which events are fabric-sensitive in the XML. The required FabricIndex field is then synthesized by ZAP, so we don't want it in the XML anymore. This fixes the naming of the FabricIndex field for some of the structs involved and lays the groundwork for a per-spec implementation of LeaveEvent (which is not fabric-sensitive but has a fabric-idx-typed field).
PR #21244: Size comparison from e556daa to 2249072 Increases (6 builds for cc13x2_26x2, nrfconnect, telink)
Decreases (7 builds for bl602, cc13x2_26x2, esp32, linux)
Full report (43 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
woody-apple
deleted the
cherry-pick-a7ad1d8cd55c30bdcd6966d2e192695336166852
branch
July 27, 2022 16:16
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update stops guessing at fabric-scoping based on the types of struct/event
fields and instead explicitly says which structs are fabric-scoped and which
events are fabric-sensitive in the XML.
The required FabricIndex field is then synthesized by ZAP, so we don't want it
in the XML anymore.
This fixes the naming of the FabricIndex field for some of the structs involved
and lays the groundwork for a per-spec implementation of LeaveEvent (which is
not fabric-sensitive but has a fabric-idx-typed field).
Problem
See above. Need this to fix #21192
Change overview
See above.
Testing
Looked at the generated code. There should be no behavior changes apart from better name alignment with the spec.